test[next]: Disable iterator tests on DaCe GTIR backend #1768
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are 2 places where the
program_processor
fixture used in tests is configured:and there are four DaCe backends:
The
DACE_CPU
andDACE_GPU
backends will be the default backends, that also apply the DaCe optimization pipeline. However, these backends are disabled for now because we are awaiting #1639.The
DACE_CPU_NO_OPT
andDACE_GPU_NO_OPT
apply the lowering to SDFG but do not run the optimization pipeline. These backends are currently enabled in GT4Py tests.However, we observed failures in some iterator tests controlled by the
program_processor
fixture intests/next_tests/unit_tests/conftest.py
, onceDACE_CPU
is enabled. In this PR, we are disabling such tests: we will address these issues in a separate PR.